Method and apparatus for discovering trending terms in speech requests

ABSTRACT

Systems and processes are disclosed for discovering trending terms in automatic speech recognition. Candidate terms (e.g., words, phrases, etc.) not yet found in a speech recognizer vocabulary or having low language model probability can be identified based on trending usage in a variety of electronic data sources (e.g., social network feeds, news sources, search queries, etc.). When candidate terms are identified, archives of live or recent speech traffic can be searched to determine whether users are uttering the candidate terms in dictation or speech requests. Such searching can be done using open vocabulary spoken term detection to find phonetic matches in the audio archives. As the candidate terms are found in the speech traffic, notifications can be generated that identify the candidate terms, provide relevant usage statistics, identify the context in which the terms are used, and the like.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No. 14/839,835, filed on Aug. 28, 2015, entitled METHOD AND APPARATUS FOR DISCOVERING TRENDING TERMS IN SPEECH REQUESTS, which claims priority from U.S. Provisional Ser. No. 62/049,294, filed on Sep. 11, 2014, entitled METHOD AND APPARATUS FOR DISCOVERING TRENDING TERMS IN SPEECH REQUESTS, which are hereby incorporated by reference in their entirety for all purposes.

FIELD

This relates generally to automatic speech recognition and, more specifically, to discovering trending terms in automatic speech recognition.

BACKGROUND

Intelligent automated assistants (or virtual assistants) provide an intuitive interface between users and electronic devices. These assistants can allow users to interact with devices or systems using natural language in spoken and/or text forms. For example, a user can access the services of an electronic device by providing a spoken user input in natural language form to a virtual assistant associated with the electronic device. The virtual assistant can perform natural language processing on the spoken user input to infer the user's intent and operationalize the user's intent into tasks. The tasks can then be performed by executing one or more functions of the electronic device, and a relevant output can be returned to the user in natural language form.

In support of virtual assistants, speech-to-text transcription (e.g., dictation), and other speech applications, automatic speech recognition (ASR) systems are used to interpret user speech. These recognizers are expected to handle a wide variety of speech input, including a variety of different types of spoken requests for virtual assistants. Examples include speech and spoken requests related to web searches, knowledge questions, sending text messages, posting to social media networks, and the like. In addition, it is desirable that virtual assistants be sympathetic and fun to talk with, which can depend on having relevant and current knowledge.

Virtual assistant and speech transcription services, however, can become outdated as relevant language and knowledge changes. ASR systems and natural language understanding (NLU) systems can work well for predetermined training language, but ASR systems can have limited and relatively static vocabularies while NLU systems can be limited by expected word patterns. These systems can thus be ill-equipped to handle new names, words, phrases, requests, and the like as they are encountered or to handle fluctuations in popular terms, and updating the systems to accommodate changing language can be tedious and slow. As such, system utility can be impaired, and the user experience can suffer as a result.

Accordingly, without identifying and accommodating changes in relevant names, words, phrases, requests, and the like, speech recognizers can suffer poor recognition accuracy, which can limit speech recognition utility and negatively impact the user experience.

SUMMARY

Systems and processes are disclosed for discovering trending terms in automatic speech recognition. In one example, a candidate term can be identified based on a frequency of occurrence of the term in an electronic data source. In response to identifying the candidate term, an archive of speech traffic can be searched for the candidate term. The archive can include speech traffic of an automatic speech recognizer. The archive can be searched using phonetic matching. In response to finding the candidate term in the archive, a notification can be generated including the candidate term.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary system for recognizing speech for a virtual assistant according to various examples.

FIG. 2 illustrates a block diagram of an exemplary user device according to various examples.

FIG. 3 illustrates an exemplary process for discovering trending terms in automatic speech recognition.

FIG. 4 illustrates an exemplary diagram of identifying trending terms from various electronic data sources.

FIG. 5 illustrates a block diagram of an exemplary system for discovering trending terms in automatic speech recognition.

FIG. 6 illustrates a functional block diagram of an electronic device configured to discover trending terms in automatic speech recognition according to various examples.

DETAILED DESCRIPTION

In the following description of examples, reference is made to the accompanying drawings in which it is shown by way of illustration specific examples that can be practiced. It is to be understood that other examples can be used and structural changes can be made without departing from the scope of the various examples.

This relates to systems and processes for discovering trending terms in automatic speech recognition. In one example, candidate terms (e.g., words, phrases, etc.) not yet found in a speech recognizer vocabulary or terms with increased popularity can be identified based on trending usage in a variety of electronic data sources (e.g., social network feeds, news sources, search queries, etc.). When candidate terms are identified, archives of live or recent speech traffic can be searched to determine whether users are uttering the candidate terms in dictation or speech requests. Such searching can be done, for example, using open vocabulary spoken term detection to find phonetic matches in the audio archives. As the candidate terms are found in the speech traffic, notifications can be generated that, for example, identify the candidate terms, provide relevant usage statistics (e.g., frequency counts), identify the context in which the terms are used, and the like.

According to the various examples discussed herein, trending terms can be detected quickly, and relevant information can be gathered to efficiently update speech recognizer vocabularies as well as to train virtual assistants with the knowledge needed to handle requests associated with new trending terms. Such trending terms can be automatically detected, and a variety of useful statistics can be gathered. Such statistics can be leverage for error analysis and for updating a variety of speech driven services to better support speech requests that include these trending terms. In the context of a virtual assistant service, for example, such statistics and the various examples discussed herein can be used to improve speech request transcription by updating the ASR system vocabulary and/or language model. In addition, understanding can be improved by refining the NLU component to support trending terms identified according to the various examples. Moreover, general assistance and the user experience can be improved by making a virtual assistant more knowledgeable about trending terms, topics, phrases, and the like identified according to the various examples herein. Similarly, a virtual assistant can be made more sympathetic and personal by being trained with knowledge of identified trending terms and topics that users care about.

The various examples discussed herein can thus identify relevant terms, which can provide for accurate speech recognition of relevant and changing language. This can accordingly provide significant system utility and an enjoyable user experience. It should be understood, however, that still many other advantages can be achieved according to the various examples discussed herein.

FIG. 1 illustrates exemplary system 100 for recognizing speech for a virtual assistant according to various examples. It should be understood that speech recognition as discussed herein can be used for any of a variety of applications, including in support of a virtual assistant. In other examples, speech recognition according to the various examples herein can be used for speech transcription, voice commands, voice authentication, or the like. The terms “virtual assistant,” “digital assistant,” “intelligent automated assistant,” or “automatic digital assistant” can refer to any information processing system that can interpret natural language input in spoken and/or textual form to infer user intent, and perform actions based on the inferred user intent. For example, to act on an inferred user intent, the system can perform one or more of the following: identifying a task flow with steps and parameters designed to accomplish the inferred user intent; inputting specific requirements from the inferred user intent into the task flow; executing the task flow by invoking programs, methods, services, APIs, or the like; and generating output responses to the user in an audible (e.g., speech) and/or visual form.

A virtual assistant can be capable of accepting a user request at least partially in the form of a natural language command, request, statement, narrative, and/or inquiry. Typically, the user request seeks either an informational answer or performance of a task by the virtual assistant. A satisfactory response to the user request can include provision of the requested informational answer, performance of the requested task, or a combination of the two. For example, a user can ask the virtual assistant a question, such as, “Where am I right now?” Based on the user's current location, the virtual assistant can answer, “You are in Central Park.” The user can also request the performance of a task, for example, “Please remind me to call Mom at 4 p.m. today.” In response, the virtual assistant can acknowledge the request and then create an appropriate reminder item in the user's electronic schedule. During the performance of a requested task, the virtual assistant can sometimes interact with the user in a continuous dialogue involving multiple exchanges of information over an extended period of time. There are numerous other ways of interacting with a virtual assistant to request information or performance of various tasks. In addition to providing verbal responses and taking programmed actions, the virtual assistant can also provide responses in other visual or audio forms (e.g., as text, alerts, music, videos, animations, etc.).

An example of a virtual assistant is described in Applicants' U.S. Utility application Ser. No. 12/987,982 for “Intelligent Automated Assistant,” filed Jan. 10, 2011, the entire disclosure of which is incorporated herein by reference.

As shown in FIG. 1, in some examples, a virtual assistant can be implemented according to a client-server model. The virtual assistant can include a client-side portion executed on a user device 102, and a server-side portion executed on a server system 110. User device 102 can include any electronic device, such as a mobile phone (e.g., smartphone), tablet computer, portable media player, desktop computer, laptop computer, PDA, television, television set-top box (e.g., cable box, video player, video streaming device, etc.), wearable electronic device (e.g., digital glasses, wristband, wristwatch, brooch, armband, etc.), gaming system, home security system, home automation system, vehicle control system, or the like. User device 102 can communicate with server system 110 through one or more networks 108, which can include the Internet, an intranet, or any other wired or wireless public or private network.

The client-side portion executed on user device 102 can provide client-side functionalities, such as user-facing input and output processing and communications with server system 110. Server system 110 can provide server-side functionalities for any number of clients residing on a respective user device 102.

Server system 110 can include one or more virtual assistant servers 114 that can include a client-facing I/O interface 122, one or more processing modules 118, data and model storage 120, and an I/O interface to external services 116. The client-facing I/O interface 122 can facilitate the client-facing input and output processing for virtual assistant server 114. The one or more processing modules 118 can utilize data and model storage 120 to determine the user's intent based on natural language input, and can perform task execution based on inferred user intent. In some examples, virtual assistant server 114 can communicate with external services 124, such as telephony services, calendar services, information services, messaging services, navigation services, and the like, through network(s) 108 for task completion or information acquisition. The I/O interface to external services 116 can facilitate such communications.

Server system 110 can be implemented on one or more standalone data processing devices or a distributed network of computers. In some examples, server system 110 can employ various virtual devices and/or services of third-party service providers (e.g., third-party cloud service providers) to provide the underlying computing resources and/or infrastructure resources of server system 110.

Although the functionality of the virtual assistant is shown in FIG. 1 as including both a client-side portion and a server-side portion, in some examples, the functions of an assistant (or speech recognition in general) can be implemented as a standalone application installed on a user device. In addition, the division of functionalities between the client and server portions of the virtual assistant can vary in different examples. For instance, in some examples, the client executed on user device 102 can be a thin-client that provides only user-facing input and output processing functions, and delegates all other functionalities of the virtual assistant to a backend server.

FIG. 2 illustrates a block diagram of an exemplary user device 102 according to various examples. As shown, user device 102 can include a memory interface 202, one or more processors 204, and a peripherals interface 206. The various components in user device 102 can be coupled together by one or more communication buses or signal lines. User device 102 can further include various sensors, subsystems, and peripheral devices that are coupled to the peripherals interface 206. The sensors, subsystems, and peripheral devices can gather information and/or facilitate various functionalities of user device 102.

For example, user device 102 can include a motion sensor 210, a light sensor 212, and a proximity sensor 214 coupled to peripherals interface 206 to facilitate orientation, light, and proximity sensing functions. One or more other sensors 216, such as a positioning system (e.g., a GPS receiver), a temperature sensor, a biometric sensor, a gyroscope, a compass, an accelerometer, and the like, can also be connected to peripherals interface 206, to facilitate related functionalities.

In some examples, a camera subsystem 220 and an optical sensor 222 can be utilized to facilitate camera functions, such as taking photographs and recording video clips. Communication functions can be facilitated through one or more wired and/or wireless communication subsystems 224, which can include various communication ports, radio frequency receivers and transmitters, and/or optical (e.g., infrared) receivers and transmitters. An audio subsystem 226 can be coupled to speakers 228 and microphone 230 to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions.

In some examples, user device 102 can further include an I/O subsystem 240 coupled to peripherals interface 206. I/O subsystem 240 can include a touchscreen controller 242 and/or other input controller(s) 244. Touchscreen controller 242 can be coupled to a touchscreen 246. Touchscreen 246 and the touchscreen controller 242 can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, such as capacitive, resistive, infrared, and surface acoustic wave technologies, proximity sensor arrays, and the like. Other input controller(s) 244 can be coupled to other input/control devices 248, such as one or more buttons, rocker switches, a thumb-wheel, an infrared port, a USB port, and/or a pointer device, such as a stylus.

In some examples, user device 102 can further include a memory interface 202 coupled to memory 250. Memory 250 can include any electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, a portable computer diskette (magnetic), a random access memory (RAM) (magnetic), a read-only memory (ROM) (magnetic), an erasable programmable read-only memory (EPROM) (magnetic), a portable optical disc such as CD, CD-R, CD-RW, DVD, DVD-R, or DVD-RW, or flash memory such as compact flash cards, secured digital cards, USB memory devices, memory sticks, and the like. In some examples, a non-transitory computer-readable storage medium of memory 250 can be used to store instructions (e.g., for performing some or all of process 300, described below) for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device, and can execute the instructions. In other examples, the instructions (e.g., for performing process 300, described below) can be stored on a non-transitory computer-readable storage medium of server system 110, or can be divided between the non-transitory computer-readable storage medium of memory 250 and the non-transitory computer-readable storage medium of server system 110. In the context of this document, a “non-transitory computer readable storage medium” can be any medium that can contain or store the program for use by or in connection with the instruction execution system, apparatus, or device.

In some examples, memory 250 can store an operating system 252, a communication module 254, a graphical user interface module 256, a sensor processing module 258, a phone module 260, and applications 262. Operating system 252 can include instructions for handling basic system services and for performing hardware-dependent tasks. Communication module 254 can facilitate communicating with one or more additional devices, one or more computers, and/or one or more servers. Graphical user interface module 256 can facilitate graphic user interface processing. Sensor processing module 258 can facilitate sensor-related processing and functions. Phone module 260 can facilitate phone-related processes and functions. Application module 262 can facilitate various functionalities of user applications, such as electronic messaging, web browsing, media processing, navigation, imaging, and/or other processes and functions.

As described herein, memory 250 can also store client-side virtual assistant instructions (e.g., in a virtual assistant client module 264) and various user data 266 (e.g., user-specific vocabulary data, preference data, and/or other data such as the user's electronic address book, to-do lists, shopping lists, etc.) to, for example, provide the client-side functionalities of the virtual assistant. User data 266 can also be used in performing speech recognition in support of the virtual assistant or for any other application.

In various examples, virtual assistant client module 264 can be capable of accepting voice input (e.g., speech input), text input, touch input, and/or gestural input through various user interfaces (e.g., I/O subsystem 240, audio subsystem 226, or the like) of user device 102. Virtual assistant client module 264 can also be capable of providing output in audio (e.g., speech output), visual, and/or tactile forms. For example, output can be provided as voice, sound, alerts, text messages, menus, graphics, videos, animations, vibrations, and/or combinations of two or more of the above. During operation, virtual assistant client module 264 can communicate with the virtual assistant server using communication subsystem 224.

In some examples, virtual assistant client module 264 can utilize the various sensors, subsystems, and peripheral devices to gather additional information from the surrounding environment of user device 102 to establish a context associated with a user, the current user interaction, and/or the current user input. In some examples, virtual assistant client module 264 can provide the contextual information or a subset thereof with the user input to the virtual assistant server to help infer the user's intent. The virtual assistant can also use the contextual information to determine how to prepare and deliver outputs to the user. The contextual information can further be used by user device 102 or server system 110 to support accurate speech recognition, as discussed herein.

In some examples, the contextual information that accompanies the user input can include sensor information, such as lighting, ambient noise, ambient temperature, images or videos of the surrounding environment, distance to another object, and the like. The contextual information can further include information associated with the physical state of user device 102 (e.g., device orientation, device location, device temperature, power level, speed, acceleration, motion patterns, cellular signal strength, etc.) or the software state of user device 102 (e.g., running processes, installed programs, past and present network activities, background services, error logs, resources usage, etc.). Any of these types of contextual information can be provided to virtual assistant server 114 (or used on user device 102 itself) as contextual information associated with a user input.

In some examples, virtual assistant client module 264 can selectively provide information (e.g., user data 266) stored on user device 102 in response to requests from virtual assistant server 114 (or it can be used on user device 102 itself in executing speech recognition and/or virtual assistant functions). Virtual assistant client module 264 can also elicit additional input from the user via a natural language dialogue or other user interfaces upon request by virtual assistant server 114. Virtual assistant client module 264 can pass the additional input to virtual assistant server 114 to help virtual assistant server 114 in intent inference and/or fulfillment of the user's intent expressed in the user request.

In various examples, memory 250 can include additional instructions or fewer instructions. Furthermore, various functions of user device 102 can be implemented in hardware and/or in firmware, including in one or more signal processing and/or application specific integrated circuits.

It should be understood that system 100 is not limited to the components and configuration shown in FIG. 1, and user device 102 is likewise not limited to the components and configuration shown in FIG. 2. Both system 100 and user device 102 can include fewer or other components in multiple configurations according to various examples.

FIG. 3 illustrates exemplary process 300 for discovering trending terms in automatic speech recognition. Process 300 can, for example, be executed on processing modules 118 of server system 110 discussed above with reference to FIG. 1. In other examples, process 300 can be executed on processor 204 of user device 102 discussed above with reference to FIG. 2. In still other examples, processing modules 118 of server system 110 and processor 204 of user device 102 can be used together to execute some or all of process 300.

At block 302, a candidate term can be identified based on a frequency of occurrence in an electronic data source. In one example, one or more electronic data sources can be referenced to identify terms that are not in a vocabulary associated with a speech recognizer or virtual assistant (e.g., by comparing terms found in a source with known vocabulary terms). The frequency of occurrence of these terms can then be determined. In particular, it can be determined whether these terms are trending or appearing frequently in the electronic data sources. Candidate terms can then be selected based on the determined frequency (e.g., selecting the most common or frequently appearing terms). In one example, the term having the highest frequency of occurrence in an electronic data source can be selected as a candidate term.

A variety of electronic data sources can be used to identify candidate terms. In some examples, electronic data sources can include any text source. In one example, an electronic data source can include a social media feed, such as messages or posts on a social networking site. In another example, an electronic data source can include a news source, such as online news websites, news feeds, email messages, and the like. In yet another example, an electronic data source can include search histories, such as trending terms used in Internet searches, terms used in computer searches, terms used in Internet browser searches, terms used in online store searches, and the like. In still other examples, an electronic data source can include a media provider that can identify popular song titles, artist names, television program titles, actor names, or the like.

In some examples, services (e.g., external or third-party services with defined application programming interfaces) can be used to identify trending terms, and candidate terms can be identified based on whether they are represented in a vocabulary associated with a speech recognizer or virtual assistant or whether they have a relatively low language model probability compared to their trending use. For example, a service associated with an Internet search engine can provide popular web searches, trending topics, trending terms, or the like. In another example, a service associated with a social network can provide terms or topics that may be appearing frequently in social media posts, messages, and the like. In yet another example, a service associated with computer search tools (e.g., browser search tools, desktop search tools, etc.) can provide terms or topics that may frequently appear in live or recent searches. A variety of other services can likewise be used to identify trending terms in, for example, other kinds of Internet traffic. With trending terms identified, candidate terms can be selected based on whether these trending terms are found in a vocabulary associated with a speech recognizer or virtual assistant (e.g., selecting out-of-vocabulary terms as candidate terms) or based on whether they have a relatively low language model probability compared to their trending use (e.g., selecting recognized terms that have a relatively low language model probability in the speech recognizer compared to their frequent use in data sources).

In any of the various examples discussed herein, candidate terms can include phrases of two or more words. For example, although a candidate term can include a single word (whether out-of-vocabulary or already recognized), in other instances, a candidate term can include a phrase of two or more words identified as a trending phrase. In some examples, trending phrases can have meaning beyond the individual words of the phrases. For example, when a hurricane is referred to by a name like “Evangelina,” users may search for the entire phrase “Hurricane Evangelina.” The phrase “Hurricane Evangelina” can be identified as a trending term in searches. The complete phrase can be used in recognition vocabularies and language models, which can improve recognition accuracy.

In one example, each of the words of a phrase may be represented in a vocabulary associated with a speech recognizer or virtual assistant (the word “hurricane” and the name “Evangelina”). The phrase, however, can be out-of-vocabulary in the sense that it may not be found as a complete phrase in a vocabulary or language model associated with a speech recognizer or virtual assistant. In another example, the phrase may be present in a language model, but the probability ascribed to the phrase may be incongruent with recent trending usage. In yet another example, the individual words making up a trending phrase can have probabilities that are relatively low compared to recent trending usage (e.g., a low probability ascribed to “hurricane” and/or to “Evangelina”). In any of these examples, the phrase and/or the individual words of the phrase can be identified as trending candidate terms based on these characteristics. Candidate terms can thus include phrases of two or more words that can be added to a vocabulary or language model as a combined entity (e.g., a multi-word token) rather than separate, individual words; and candidate terms can likewise include individual words of a phrase that can have higher probabilities assigned to them based on a mismatch between trending usage and an inconsistent low language model probability. For example, a sufficiently high probability can be assigned to the phrase “Hurricane Evangelina” by adding the bi-gram “Hurricane Evangelina” to the language model or by increasing the probability of both unigrams “Hurricane” and “Evangelina.”

Referring again to process 300 of FIG. 3, at block 304, an archive of speech traffic can be searched for the identified candidate terms. In one example, live and/or recent speech traffic for a speech recognizer or virtual assistant can be collected and archived. In some examples, the archives can include speech audio. In other examples, the archives can include ASR recognition lattices (e.g., data structures that can include a ranked list of potential interpretations of speech or phonetic representations of speech). In other examples, the archives can include a phonetically indexed speech recognition lattice that can, for example, be quickly searchable for phonetic sequences. In some examples, archives can include addition information associated with a speech sample, such as information collected when the speech sample was received. Such additional information can include a system response (e.g., error message, result, output, etc.), a user identification, an anonymized user profile, a geographic location, a device type, a timestamp, or the like.

In one example, searching the speech traffic archives can include using an open vocabulary spoken term detection system to find the candidate terms in the archive. An open vocabulary spoken term detection system can rapidly sift through archived speech traffic. Such systems can, for example, employ phonetically indexed speech recognition lattices for fast and readily scalable searching based on phonetic sequences. In some examples, fuzzy matching can be used in searching a speech traffic archive for a candidate term. Fuzzy matching can include searching for a candidate term's likely pronunciation (e.g., phonetic representation) as well as for similar variants. In one example, archives can include ASR lattices for speech samples, so the detection system can simply search according to a given lattice format. In other examples, archives can include speech audio samples, so the detection system can generate a readily searchable phonetically indexed speech recognition lattice in order to search the audio samples.

FIG. 4 illustrates an exemplary diagram 400 of identifying trending terms from various electronic data sources. As illustrated, in the various examples discussed herein, relevant trending terms can be identified based on overlapping term usage in multiple sources. For example, relevant trending terms can be identified from social network feed 410, news sources 412, and other data sources 414 (e.g., search histories, media providers, etc.). For those terms found to be out-of-vocabulary for a speech recognizer or virtual assistant or found to have a relatively low language model probability compared to their trending use, speech traffic 416 can be checked for instances of the same trending terms (e.g., overlapping usage in social network feed 410 and speech traffic 416, overlapping usage in news sources 412 and speech traffic 416, etc.). Thus, as described with reference to blocks 302 and 304 of process 300, relevant terms can be identified based on candidate terms found in both an electronic data source and speech traffic. The identified terms from the overlap illustrated in diagram 400 (or equivalently resulting from blocks 302 and 304 of process 300) can, in some examples, provide highly relevant trending terms, inclusion of which in an ASR vocabulary or language model (or increased probability of which) can have a significant impact on recognition accuracy and utility.

Referring again to process 300 of FIG. 3, at block 306, after finding the candidate terms in a speech traffic archive, a notification can be generated including the candidate term. Such a notification can include a message, pop-up, statistic, report, summary, chart, table, graphic, or any of a variety of other notifications that can identify a relevant term. Should a term not be found in a speech archive, the term may be less relevant for an ASR system than terms that are identified in speech archives. Terms that are not found in speech archives can be identified in a different notification (e.g., indicating a trending term has been found in electronic data sources but not yet in speech traffic). Such terms can be saved for later reference (e.g., to continue checking speech archives for possible trends).

In some examples, in response to finding the candidate term in a speech archive, a variety of statistics can be generated associated with that term, and those statistics can be included in the notification for that term. For example, a statistic can be generated based on a frequency of occurrence of the candidate term in the archive. Such a statistic can, for example, reflect how many users may be attempting to utter the candidate term in speech requests or dictation. In one example, a frequency count can be generated for various recent time periods (e.g., instances in the last hour, instances in the last day, instances in the last week, etc.).

In another example, the notification with the candidate term can also include a context associated with the candidate term found in the archive. Such context can include one or more words adjacent to the candidate term in the archive (e.g., words in an associated sentence, an associated speech request, an associated utterance, etc.). Such context can reflect how the candidate term appeared in a particular utterance, which can, for example, be useful for language modeling. In one example, the context can include a user request for a virtual assistant, where the candidate term appears in the user request. Such user requests can be used to train a virtual assistant to handle future requests of the same type. In some examples, statistics can be generated regarding the context surrounding instances of a candidate term. For example, a statistic can be generated reflecting the frequency with which a candidate term appears in conjunction with certain words, phrases, requests, or the like.

Context surrounding a candidate term can be derived from an ASR transcription, speech audio, an external data source (e.g., social media feed, news source, etc.), or the like. In one example, context derived from an ASR transcription can be used to identify a relevant domain of a virtual assistant system. With a relevant domain identified, the virtual assistant system can be trained to handle requests associated with the candidate term within that domain. Such context that may be useful for training a virtual assistant system may not be available from electronic data sources (e.g., social media feeds, news sources, etc.), so identifying relevant terms in both electronic data sources and in speech traffic can provide additional information that can be highly valuable in training virtual assistant systems.

In one example, speech recognition can be performed again on archived speech traffic to generate a transcription after, for example, language models and/or vocabularies have been updated with trending terms. The transcription can then be used to derive and provide context surrounding the candidate term in speech samples. In one example, speech recognition can be performed on a portion or subset of recent audio (e.g., a random sample). By running the speech recognizer on archival materials, full transcripts can be obtained that can be a source for context that can be used according to various examples discussed herein. In one example, such context can be used to modify a natural language processing component of the system. In some examples, this process can be iterated. For instance, once revised transcripts have been computed, language model statistics (e.g., word frequencies, n-gram frequencies, etc.) can be computed and combined with statistics from other sources (e.g., text sources). Those statistics can then be used to further modify the recognizer's language model, and speech recognition can then be repeated on the same or different archived speech traffic samples. The resulting transcript can then be used to derive additional statistics, and the process can be iteratively repeated to further refine the recognizer's language model.

In other examples, the notification with the candidate term can also include a variety of other contextual information associated with instances of a candidate term in a speech archive. Statistics can also be generated based on such information, and the statistics can be provided in the notification along with the candidate term. For example, a notification can include additional context, such as a geographical location associated with occurrences of the candidate term in a speech archive. Such information can be derived from metadata associated with an archived utterance and can reflect approximate geographical locations of users who uttered the term (e.g., based on GPS, cell phone tower localization, Wi-Fi location, IP address location, etc.). In another example, a notification can include additional context information, such as user profiles associated with occurrences of the candidate term in a speech archive. Such information can reflect anonymized characteristics, demographics, and the like of users who uttered the term. In another example, a notification can include other contextual or characterizing information, such as device type (e.g., the type of device used to capture an utterance), a particular state of a device (e.g., running applications, device usage statistics, etc.), user group (e.g., broad categories of user types, such as age range, gender, subscription plans, etc.), or any of a variety of other information that can be associated with utterances that include a candidate term.

In still other examples, the notification with the candidate term can also include system responses, system context, interaction context, or the like associated with occurrences of a candidate term in a speech archive. Statistics can also be generated based on such information, and the statistics can be provided in the notification along with the candidate term. In one example, the notification can include an error associated with an occurrence of the candidate term, such as a system error code generated when the term was not recognized, when the user indicated the system made a mistake, when the system defaulted to a web search to resolve a query, or the like. Such errors can include transcription errors, where a user may have manually corrected an incorrectly transcribed utterance, as well as virtual assistant errors, in which a virtual assistant took an action that the user may not have intended. Interaction context can also be provided that can reflect user interactions surrounding an utterance of a candidate term (e.g., previous queries, subsequent queries, applications used, actions taken, etc.).

It should be understood that the notification generated at block 306 of process 300 can include a variety of information, including collective statistics associated with multiple occurrences of a candidate term in a speech archive. It should further be understood that such notifications can include any of a variety of other information associated with instances where a user uttered a candidate term as well as any of a variety of other statistical information garnered from information associated with those instances.

In some examples, the identification of relevant trending terms (along with associated statistics in some examples) can be used in a variety of ways to improve vocabularies and language models associated with speech recognizers and virtual assistants. In one example, identified candidate terms can be added to a vocabulary associated with an ASR system. In another example, a virtual assistant can be trained to respond to queries associated with an identified candidate term. Statistics discussed above indicating the context surrounding instances of a candidate term in speech traffic can be used to determine anticipated requests and usage, which can, for example, be incorporated into a language model to improve recognition and response accuracy. In one example, an n-gram language model associated with an automatic speech recognizer can be updated based on identified candidate terms, context, and/or statistics discussed above.

In other examples, the identification of relevant trending terms and associated statistics can be used in a variety of other ways to provide system utility and an enjoyable user experience. In one example, error analysis can be conducted based on the terms and statistics information discussed above. Such error information can be used to correct virtual assistant errors, prioritize areas for correction, identify groups of utterances that may be difficult to recognize, or the like. In another example, identified terms and statistics can be used for targeted advertising associated with identified terms (e.g., advertising to users who uttered a relevant term). In yet another example, identified terms and statistics can be used to personalize systems for different user groups (e.g., groups of users having similar characteristics). Such personalization can include customized vocabularies, grammars, language models, and the like. Such personalization can also include targeted advertising to particular groups based on members of the group using certain terms.

In another example, identified terms and statistics can be used to reveal trends in language, requests, interactions, and the like, which can be used to improve system functionality. Moreover, according to the various examples herein, speech audio samples can be identified that can be used for training speech recognition systems. For example, speech audio samples can be re-recognized using newly-trained models to verify accurate recognition. It should be understood that relevant terms and associated data identified according to the various examples discussed herein can be used in a variety of other ways to improve speech recognizer performance, reveal useful trend information, monitor system performance, and the like.

FIG. 5 illustrates a block diagram of an exemplary system 500 for discovering trending terms in automatic speech recognition. In one example, system 500 can include a candidate term spotter 520, spoken term detector 522, speech traffic archiver 524, and analyzer 526. In some examples, candidate term spotter 520 can provide a periodically updated list of candidate terms (e.g., trending terms). The list of candidate terms can be compiled from external data sources that may be relevant to a speech recognizer. External data sources can include social network feeds, news sources, media providers, messages, chats, search queries, websites, or any other sources. In some examples, application programming interfaces can provide access to trending terms directly based on the external data sources.

Speech traffic archiver 524 can store speech audio and/or ASR recognition lattices derived from live speech traffic of an ASR system. In some examples, speech traffic archiver 524 can store recent speech traffic from within a certain time period (e.g., within the last week, within the last day, etc.). Speech traffic archiver 524 can store a variety of additional information along with speech samples, including system responses (e.g., error messages), user group identification, geographic location, device type, or the like.

Spoken term detector 522 can include an open vocabulary spoken term detection system that can rapidly sift through speech audio accumulated by speech traffic archiver 524 to find instances of the candidate terms identified by candidate term spotter 520. Such systems can operate quickly and scale well by employing phonetically indexed speech recognition lattices. Spoken term detector 522 can also employ fuzzy matching of a candidate term's likely pronunciation (e.g., phonetic representation) with phonetic sequences found in speech recognition lattices. In one example, given a particular lattice format, spoken term detector 522 can operate directly on an ASR lattice provided by speech traffic archiver 524.

Analyzer 526 can compile relevant statistics with regard to candidate terms discovered in speech traffic by spoken term detector 522. Such statistics can include frequency counts for various recent time periods; correlations of trending terms with system responses (e.g., error messages); correlations of trending terms with locality, device type, user group, etc.; statistics regarding word context in which candidate terms may appear (e.g., derived from an ASR transcription or external data source); and the like. Information derived by analyzer 526 can be used in downstream processing for a variety of purposes, such as adding candidate terms to vocabularies and language models of speech recognizers and virtual assistants or training virtual assistants to respond to queries related to candidate terms.

In addition, in any of the various examples discussed herein, various aspects can be personalized for a particular user. The various processes discussed herein can be modified according to user preferences, contacts, text, usage history, profile data, demographics, or the like. In addition, such preferences and settings can be updated over time based on user interactions (e.g., frequently uttered commands, frequently selected applications, etc.). Gathering and use of user data that is available from various sources can be used to improve the delivery to users of invitational content or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data can include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information.

The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.

The present disclosure further contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data as private and secure. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection should occur only after receiving the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices.

Despite the foregoing, the present disclosure also contemplates examples in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of advertisement delivery services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services. In another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select not to provide precise location information, but permit the transfer of location zone information.

Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed examples, the present disclosure also contemplates that the various examples can also be implemented without the need for accessing such personal information data. That is, the various examples of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services, or publicly available information.

In accordance with some examples, FIG. 6 shows a functional block diagram of an electronic device 600 configured in accordance with the principles of the various described examples. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 6 can be combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 6, electronic device 600 can include an input interface unit 602 configured to receive information (e.g., through a network, from another device, from a hard drive, etc.). Electronic device 600 can further include an output interface unit 604 configured to output information (e.g., through a network, to another device, to a hard drive, etc.). Electronic device 600 can further include processing unit 606 coupled to input interface unit 602 and output interface unit 604. In some examples, processing unit 606 can include a candidate term identifying unit 608, a speech archive searching unit 610, and a notification generating unit 612.

Processing unit 606 can be configured to identify (e.g., using candidate term identifying unit 608) a candidate term based on a frequency of occurrence of the term in an electronic data source. Processing unit 606 can be further configured to, in response to identifying the candidate term, search (e.g., using speech archive searching unit 610) for the candidate term in an archive of speech traffic of an automatic speech recognizer using phonetic matching. Processing unit 606 can be further configured to, in response to finding the candidate term in the archive, generate (e.g., using notification generating unit 612) a notification comprising the candidate term.

In some examples, the electronic data source comprises text. In one example, the electronic data source comprises a social media feed. In another example, the electronic data source comprises a news source. In yet another example, the electronic data source comprises a search history. In one example, identifying the candidate term comprises identifying one or more terms in the electronic data source, determining a frequency of occurrence of the one or more terms in the electronic data source, and selecting the candidate term based on the determined frequency of occurrence of the one or more terms. In some examples, selecting the candidate term comprises selecting from the one or more terms a term having a highest frequency of occurrence in the electronic data source.

In some examples, the candidate term comprises a phrase of two or more words. In one example, the archive of speech traffic comprises speech audio. In another example, the archive of speech traffic comprises a phonetically indexed speech recognition lattice. In other examples, searching the archive comprises using open vocabulary spoken term detection to find the candidate term in the archive. In still other examples, searching the archive comprises using fuzzy matching to find the candidate term in the archive.

In other examples, processing unit 606 can be further configured to, in response to finding the candidate term in the archive, generate a statistic based on a frequency of occurrence of the candidate term in the archive; wherein the notification comprises the statistic. In one example, the notification comprises a context associated with the candidate term found in the archive. In another example, the context comprises one or more words adjacent to the candidate term in the archive. In yet another example, the context comprises a user request for a virtual assistant, wherein the user request comprises the candidate term.

In some examples, the notification comprises a geographical location associated with an occurrence of the candidate term in the archive. In other examples, the notification comprises a user profile associated with an occurrence of the candidate term in the archive. In still other examples, the notification comprises an error associated with an occurrence of the candidate term in the archive. In one example, processing unit 606 can be further configured to add the candidate term to a vocabulary associated with the automatic speech recognizer. In another example, processing unit 606 can be further configured to train a virtual assistant to respond to queries associated with the candidate term. In yet another example, processing unit 606 can be further configured to update an n-gram language model associated with the automatic speech recognizer based on the candidate term.

In some example, the candidate term is out-of-vocabulary for the automatic speech recognizer. In one example, identifying the candidate term comprises identifying one or more terms in the electronic data source that are not found in a vocabulary of the automatic speech recognizer, determining a frequency of occurrence of the one or more terms in the electronic data source, and selecting the candidate term based on the determined frequency of occurrence of the one or more terms. In some examples, selecting the candidate term comprises selecting from the one or more terms a term having a highest frequency of occurrence in the electronic data source.

In another example, identifying the candidate term comprises identifying the candidate term based on a speech recognizer language model probability associated with the candidate term. In one example, the language model probability is low compared to the frequency of occurrence of the candidate term. In yet another example, processing unit 606 can be further configured to transcribe a portion of the archive of speech traffic using the automatic speech recognizer. Processing unit 606 can be further configured to determine and provide context based on the transcribed portion of the archive of speech traffic.

Although examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art (e.g., modifying any of the systems or processes discussed herein according to the concepts described in relation to any other system or process discussed herein). Such changes and modifications are to be understood as being included within the scope of the various examples as defined by the appended claims. 

What is claimed is:
 1. A method for discovering trending terms in automatic speech recognition, the method comprising: at an electronic device having a processor and memory: identifying a candidate term based on a frequency of occurrence of the term in one or more electronic data sources; in response to identifying the candidate term, searching for the candidate term in an archive of speech traffic of an automatic speech recognizer using phonetic matching; and in response to finding the candidate term in the archive, updating a vocabulary of the automatic speech recognizer with the candidate term.
 2. The method of claim 1, wherein identifying the candidate term comprises: identifying one or more terms in the one or more electronic data sources; determining a frequency of occurrence of the one or more terms in the one or more electronic data sources; and selecting the candidate term based on the determined frequency of occurrence of the one or more terms.
 3. The method of claim 1, wherein the one or more electronic data sources include a news source or a social media feed.
 4. The method of claim 1, wherein the one or more electronic data sources include a search history of a search engine.
 5. The method of claim 1, wherein the archive of speech traffic comprises a phonetically indexed speech recognition lattice.
 6. The method of claim 1, wherein the one or more electronic data sources include at least one electronic data source external to the electronic device.
 7. The method of claim 1, further comprising: in response to finding the candidate term in the archive, refining a natural language understanding component of a virtual assistant using the candidate term.
 8. The method of claim 1, further comprising: in response to finding the candidate term in the archive, updating a language model of the automatic speech recognizer based on the candidate term.
 9. The method of claim 8, further comprising: in response to finding the candidate term in the archive, generating a statistic based on a frequency of occurrence of the candidate term in the archive, wherein the language model is updated based on the generated statistic.
 10. The method of claim 9, further comprising: obtaining a word context of the candidate term in the archive, wherein the language model is updated based on the obtained word context.
 11. The method of claim 1, wherein prior to updating the vocabulary, the vocabulary does not include the candidate term.
 12. The method of claim 1, wherein identifying the candidate term further comprises: identifying the candidate term based on a speech recognizer language model probability associated with the candidate term.
 13. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs including instructions for: identifying a candidate term based on a frequency of occurrence of the term in one or more electronic data sources; in response to identifying the candidate term, searching for the candidate term in an archive of speech traffic of an automatic speech recognizer using phonetic matching; and in response to finding the candidate term in the archive, updating a vocabulary of the automatic speech recognizer with the candidate term.
 14. The computer-readable storage medium of claim 13, wherein the archive of speech traffic comprises a phonetically indexed speech recognition lattice.
 15. The computer-readable storage medium of claim 13, the one or more programs further including instructions for: in response to finding the candidate term in the archive, refining a natural language understanding component of a virtual assistant using the candidate term.
 16. The computer-readable storage medium of claim 13, the one or more programs further including instructions for: in response to finding the candidate term in the archive, updating a language model of the automatic speech recognizer based on the candidate term.
 17. The computer-readable storage medium of claim 16, the one or more programs further including instructions for: in response to finding the candidate term in the archive, generating a statistic based on a frequency of occurrence of the candidate term in the archive, wherein the language model is updated based on the generated statistic.
 18. The computer-readable storage medium of claim 13, wherein prior to updating the vocabulary, the vocabulary does not include the candidate term.
 19. An electronic device, comprising: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: identifying a candidate term based on a frequency of occurrence of the term in one or more electronic data sources; in response to identifying the candidate term, searching for the candidate term in an archive of speech traffic of an automatic speech recognizer using phonetic matching; and in response to finding the candidate term in the archive, updating a vocabulary of the automatic speech recognizer with the candidate term.
 20. The device of claim 19, wherein the archive of speech traffic comprises a phonetically indexed speech recognition lattice.
 21. The device of claim 19, the one or more programs further including instructions for: in response to finding the candidate term in the archive, refining a natural language understanding component of a virtual assistant using the candidate term.
 22. The device of claim 19, the one or more programs further including instructions for: in response to finding the candidate term in the archive, updating a language model of the automatic speech recognizer based on the candidate term.
 23. The device of claim 22, the one or more programs further including instructions for: in response to finding the candidate term in the archive, generating a statistic based on a frequency of occurrence of the candidate term in the archive, wherein the language model is updated based on the generated statistic.
 24. The device of claim 19, wherein prior to updating the vocabulary, the vocabulary does not include the candidate term.
 25. The non-transitory computer readable storage medium of claim 17, the one or more programs further including instructions for: obtaining a word context of the candidate term in the archive, wherein the language model is updated based on the obtained word context.
 26. The non-transitory computer readable storage medium of claim 13, wherein identifying the candidate term comprises: identifying one or more terms in the one or more electronic data sources; determining a frequency of occurrence of the one or more terms in the one or more electronic data sources; and selecting the candidate term based on the determined frequency of occurrence of the one or more terms.
 27. The non-transitory computer readable storage medium of claim 13, wherein the one or more electronic data sources include a news source or a social media feed.
 28. The non-transitory computer readable storage medium of claim 13, wherein the one or more electronic data sources include a search history of a search engine.
 29. The non-transitory computer readable storage medium of claim 13, wherein the one or more electronic data sources include at least one electronic data source external to the electronic device.
 30. The non-transitory computer readable storage medium of claim 13, wherein identifying the candidate term further comprises: identifying the candidate term based on a speech recognizer language model probability associated with the candidate term.
 31. The electronic device of claim 23, the one or more programs further including instructions for: obtaining a word context of the candidate term in the archive, wherein the language model is updated based on the obtained word context.
 32. The electronic device of claim 19, wherein identifying the candidate term comprises: identifying one or more terms in the one or more electronic data sources; determining a frequency of occurrence of the one or more terms in the one or more electronic data sources; and selecting the candidate term based on the determined frequency of occurrence of the one or more terms.
 33. The electronic device of claim 19, wherein the one or more electronic data sources include a news source or a social media feed.
 34. The electronic device of claim 19, wherein the one or more electronic data sources include a search history of a search engine.
 35. The electronic device of claim 19, wherein the one or more electronic data sources include at least one electronic data source external to the electronic device.
 36. The electronic device of claim 19, wherein identifying the candidate term further comprises: identifying the candidate term based on a speech recognizer language model probability associated with the candidate term.
 37. The method of claim 1, further comprising: performing speech recognition using the updated vocabulary of the automatic speech recognizer.
 38. The non-transitory computer-readable storage medium of claim 13, the one or more programs further including instructions for: performing speech recognition using the updated vocabulary of the automatic speech recognizer.
 39. The electronic device of claim 19, the one or more programs further including instructions for: performing speech recognition using the updated vocabulary of the automatic speech recognizer. 